Systems and methods for relationship management

ABSTRACT

A relationship management system and method are configured to enable a user to manage a relationship with their contacts from the initial interaction through the life cycle of a transaction or relationship and beyond. For example, a relationship management system may record and sort all communications (for example, phone calls, text messages, and emails) into a contact&#39;s profile, empowering a user to easily see the entire relationship at a glance. Moreover, using actionable business intelligence, an exemplary relationship management system may utilize a workflow engine to send notifications, schedule tasks, and allow users to see reports, thus allowing a user to increase productivity and save time. Exemplary relationship management systems are configured for use in the multi-family housing industry.

CROSS-REFERENCE TO RELATED APPLICATION

This application is a continuation of U.S. Ser. No. 14/740,562, filed onJun. 16, 2015 and entitled “SYSTEMS AND METHODS FOR RELATIONSHIPMANAGEMENT”. U.S. Ser. No. 14/740,562 claims priority to and the benefitof Provisional Application No. 62/012,809, filed on Jun. 16, 2014 andentitled “SYSTEMS AND METHODS FOR RELATIONSHIP MANAGEMENT.” The entirecontents of all the foregoing applications are hereby incorporated byreference.

TECHNICAL FIELD

The present disclosure generally relates to mobile applications, andmore particularly, to methods and systems for the management andorganization of communications information received from multiplesources using multiple methods of communication.

BACKGROUND

In today's world, there are countless communication methods available tosend communications. Accordingly, everyone is constantly receivingcommunications from multiple sources, whether it is from a mobile phonetext message, email, voicemail, social media message, etc. This overloadof information may cause confusion and miscommunication ascommunications are misplaced or forgotten.

Some forms of communication are easily consolidated, such as calendarsand emails sharing data between mobile phones and computers. However,there may still be communications from other people or different sourcesthat get lost in the mix. Accordingly, there is a shortfall incommunication organization because there is no method for organizing alldata received through various communication types with others from allsources.

SUMMARY

In accordance with principles of the present disclosure, a relationshipmanagement system and method are configured to enable a user to manage arelationship with their contacts from the initial interaction throughthe life cycle of a transaction or relationship and beyond. For example,a relationship management system may record and sort all communicationsinto a contact's profile, empowering a user to easily see the entirerelationship at a glance. Moreover, using actionable businessintelligence, an exemplary relationship management system may utilize aworkflow engine to send notifications, schedule tasks, and allow usersto see reports, thus allowing a user to increase productivity and savetime.

In accordance with an exemplary embodiment, a relationship managementsystem comprises a user interface operable on a mobile device; a serverin communication with the user interface, the server configured toimplement business processes associated with communication informationreceived by the relationship management system; and a database incommunication with the server, the database configured to store thecommunication information received at the relationship managementsystem. The relationship management system is configured to managemultiple forms of communication information associated with a contact ofa user using actionable business intelligence to provide a workflowengine to send notifications, schedule tasks, and allow users to seereports, thus allowing a user to increase productivity and save time.

In another exemplary embodiment, a computerized method for relationshipmanagement comprises receiving, at a relationship management system, anitem of communication from a user; filtering, by a relationshipmanagement engine in the relationship management system, the item ofcommunication into at least one of a plurality of buckets; analyzing, bya workflow engine in the relationship management system, the item ofcommunication to identify at least one of a plurality of actions to takein response to the item of communication; and implementing, via a mobilesoftware application of the relationship management system, the at leastone of the plurality of actions responsive to the item of communication.

The contents of this section are intended as a simplified introductionto the disclosure, and are not intended to limit the scope of any claim.

BRIEF DESCRIPTION OF THE DRAWINGS

With reference to the following description, appended claims, andaccompanying figures, in which like reference numbers refer to likeelements or acts throughout the figures:

FIG. 1 is a block diagram of an exemplary relationship management systemin accordance with an exemplary embodiment;

FIG. 2 is a block diagram illustrating exemplary operationalcharacteristics of an exemplary relationship management system inaccordance with an exemplary embodiment;

FIG. 3A illustrates exemplary data and process flows in an exemplaryrelationship management system in accordance with an exemplaryembodiment;

FIG. 3B illustrates exemplary functional components and data/processflows of an exemplary relationship management system in accordance withan exemplary embodiment;

FIG. 3C illustrates an exemplary technology architecture for anexemplary relationship management system in accordance with an exemplaryembodiment;

FIG. 3D illustrates an exemplary architecture for a user interfacecomponent (mobile application) of an exemplary relationship managementsystem in accordance with an exemplary embodiment;

FIG. 3E illustrates data and process flows in an exemplary relationshipmanagement system in accordance with an exemplary embodiment;

FIG. 3F illustrates a process for management of telephoniccommunications in an exemplary relationship management system inaccordance with an exemplary embodiment;

FIGS. 4A through 4R are screenshots illustrating functionality and/orconfiguration of a user interface component (mobile application) of anexemplary relationship management system in accordance with an exemplaryembodiment; and

FIGS. 5A through 5P are screenshots illustrating functionality and/orconfiguration of a user interface component (mobile application) of anexemplary relationship management system in accordance with an exemplaryembodiment.

DETAILED DESCRIPTION

The following description is of various embodiments only, and is notintended to limit the scope, applicability or configuration of thepresent disclosure in any way. Rather, the following description isintended to provide a convenient illustration for implementing variousembodiments including the best mode. As will become apparent, variouschanges may be made in the function and arrangement of the elementsdescribed in these embodiments without departing from the scope of thepresent disclosure or appended claims.

It should be appreciated that exemplary components and steps may berealized by any number of hardware, software, or other componentsconfigured to perform the specified functions. For example, an exemplaryembodiment employs various graphical user interfaces, softwarecomponents, and networking and/or database functionality. In addition,various embodiments may be practiced in any number of communicationsmanagement and/or information management contexts, and the embodimentsdisclosed are merely indicative of exemplary applications. For example,the principles, features and methods discussed may be applied to variousindustries, and are not limited to use in connection with communicationsinformation. Moreover, various exemplary embodiments are discussed inconnection with management of communications associated withmulti-family housing management; however, it will be appreciated thatprinciples of the present disclosure, and exemplary systems and/ormethods implementing the same, may suitably be applied in various otherindustries and/or contexts, for example any sales or service-relatedprofession requiring travel outside of a home office forbusiness-related transactions such as realtors, auto dealers, insuranceagents, lawyers, doctors, pest control professionals, pool serviceprofessionals, landscapers, plumbers, electricians, contractors,pharmaceutical salesmen, etc.

The detailed description of exemplary embodiments herein makes referenceto the accompanying figures, which show embodiments by way ofillustration. While these embodiments are described in sufficient detailto enable those skilled in the art to practice the disclosure, it shouldbe understood that other embodiments may be realized and that logicaland/or functional changes may be made without departing from the spiritand scope of the disclosure. Thus, the detailed description herein ispresented for purposes of illustration only and not of limitation. Forexample, the steps recited in any of the method or process descriptionsmay be executed in various orders and are not limited to the orderpresented. Moreover, certain of the functions or steps may be outsourcedto or performed by one or more third parties. Furthermore, any referenceto singular includes plural embodiments, and any reference to more thanone component may include a singular embodiment.

Systems, methods and computer program products are provided. In thedetailed description herein, references to “an exemplary embodiment”,“various embodiments”, “one embodiment”, “an embodiment”, “an exampleembodiment”, etc., indicate that the embodiment described may include aparticular feature, structure, or characteristic, but every embodimentmay not necessarily include the particular feature, structure, orcharacteristic. Moreover, such phrases are not necessarily referring tothe same embodiment. Further, when a particular feature, structure, orcharacteristic is described in connection with an embodiment, it issubmitted that it is within the knowledge of one skilled in the art toaffect such feature, structure, or characteristic in connection withother embodiments whether or not explicitly described. After reading thedescription, it will be apparent to one skilled in the relevant art(s)how to implement the disclosure in alternative embodiments.

As used herein, “match” or “associated with” or similar phrases mayinclude an identical match, a partial match, meeting certain criteria,matching a subset of data, a correlation, satisfying certain criteria, acorrespondence, an association, an algorithmic relationship and/or thelike. Similarly, as used herein, “authenticate” or similar terms mayinclude an exact authentication, a partial authentication,authenticating a subset of data, a correspondence, satisfying certaincriteria, an association, an algorithmic relationship and/or the like.

In various embodiments, the methods described herein are implementedusing the various particular machines described herein. The methodsdescribed herein may be implemented using the below particular machines,and those hereinafter developed, in any suitable combination, as wouldbe appreciated immediately by one skilled in the art. Further, as isunambiguous from this disclosure, the methods described herein mayresult in various transformations of certain articles.

For the sake of brevity, conventional techniques for data networking,software application development, cloud computing, and/or the like, maynot be described in detail herein. Furthermore, the connecting linesshown in various figures contained herein are intended to representexemplary functional relationships and/or physical or communicativecouplings between various elements. It should be noted that manyalternative or additional functional relationships or physical orcommunicative connections may be present in a practical relationshipmanagement system.

Exemplary relationship management systems configured in accordance withprinciples of the present disclosure enable a user to manage arelationship with their contacts from the initial interaction throughthe life cycle of a transaction or relationship and beyond. For example,a relationship management system may record and sort all communicationsinto a contact's profile, empowering a user to easily see the entirerelationship at a glance. Moreover, using actionable businessintelligence, an exemplary relationship management system may utilize aworkflow engine to send notifications, schedule tasks, and allow usersto see reports, thus allowing a user to increase productivity and savetime. It will be appreciated that exemplary relationship managementsystems and/or methods disclosed herein can enable a user to save time,money, and resources, for example by facilitating management of allbusiness and personal communications in one place.

In an exemplary embodiment, a “relationship management system” may beconfigured to facilitate organization, storage, and/or display ofcommunications information, for example information sent or received bya management system user. A relationship management system may also takecertain actions, for example based on communications types, usersettings, and/or the like. With reference now to FIG. 1, in an exemplaryembodiment, a relationship management system, for example system 100,may comprise a user interface component 100A, a server component 100B,and a database component 100C. User interface component 100A may beconfigured to deliver information to and/or receive information from auser. For example, system 100 may be able to send communications of anyavailable form (phone call, email, text message, etc.) via a user'sinteraction with user interface component 100A. Server component 100Bmay be configured to interact with user interface component 100A, forexample to facilitate system functionality. Database component 100C maybe configured for storage and retrieval of information utilized insystem 100, and may interact with user interface component 100A and/orserver component 100B. It will be appreciated that in various exemplaryembodiments, one or more of user interface component 100A, servercomponent 100B, and/or database component 100C may comprise multiplesub-components, systems, or elements; moreover, a single element orcomponent may offer functionality of (or be considered to be) more thanone of user interface component 100A, server component 100B, or databasecomponent 100C. For example, in an exemplary embodiment, servercomponent 100B and database component 100C may comprise a singlecomputing and/or communications resource.

In general, relationship management system 100 may comprise any systems,components, and/or modules configured with any suitable methods,algorithms, and/or techniques for communications information management,organization, action, and display. Additionally, system 100 may alsosuitably interface with any number and/or types of communications, forexample, phones, emails, text messages, manual entries, users,aggregation services routers/interactive voice responses, social mediawebsites, etc.

Turning now to FIG. 2, in various exemplary embodiments, system 100 maycomprise a relationship management engine 120, buckets 130, a workflowengine 140, and user interface 160 on some sort of display screen, suchas on a smartphone or tablet. Relationship management engine 120 mayreceive and organize any type of communications 110 and may placecommunications 110 in buckets 130, for example, based on predeterminedcriteria set by a user. Workflow engine 140 may determine actions 150taken by the system 100 in response to certain types of communications,for example based on the business rules determined by the user. Itshould be appreciated that the types of communications labeled 110 inFIG. 2 are examples, and system 100's capabilities for organizingcommunications should not be limited to those listed in the figures.Also, the term “phone call” is meant to include video calls and/or voicecalls, IP telephony, and/or the like.

In various exemplary embodiments, relationship management engine 120 maybe any engine, system, or method within system 100 configured to receivecommunications from any available source, organize it by placing it intocategorical buckets 130, and save the communications. Throughrelationship management engine 120, the user of system 100 may be ableto easily search, retrieve, edit, and/or add notes to any type ofcommunications. It should be appreciated that the functions ofrelationship management engine 120 are not limited to those listedabove, but that those are simply examples of its functionality.

Relationship management engine 120 may receive communications frommultiple sources by parsing incoming emails to have a uniform format,for example. Depending on the type of incoming communications, there maybe different ways the system 100 and relationship management engine 120receive and process inputs. For example, all phone calls may be routedto the system 100's telephony systems and all emails are forwarded tospecific email accounts associated to the system 100 user.

Relationship management engine 120 may organize communications receivedfrom multiple sources by placing the communications into categoricalbuckets 130. A user of system 100 may set relationship management engine120 to recognize certain characteristics to identify which bucket 130 inwhich to place the communications. For example, the user may set therelationship management engine 120 to recognize and identify certainphone numbers, email addresses, social media accounts, etc. and placethe recognized communications into buckets 130 based on the relationshipthe system 100 user has with the contact sending the communications.Once the contact is identified by the identifying characteristic(s) ofthe communications, the communications are placed in the appropriatecontact and bucket. For example, a contact may have a relationshipstatus to the user of system 100 of a family member, friend, businessassociate, potential client, etc., and the user may create buckets 130for each of those relationship statuses. An example of such buckets isillustrated in FIG. 4J.

If communications are received from an unknown source, the system 100may try to identify the communications as a different source from anexisting contact and merge that communication with other communicationsfrom that contact, or receive the communications and indicate to thesystem 100 user through the user interface that the contact is unknown.If multiple contacts are created for multiple sources of communications,and it turns out that all of the communications are coming from the sameperson or entity, the user may merge these multiple contacts into onecontact folder. In other words, in the event that multiple pieces ofcommunications come in under different emails or phone numbers, the usermay manually merge the contacts. Similarly, a system 100 user may beable to transfer a contact's information to another user's system, andwhen doing so, the transferring user may be prompted to add a note toinform the other user of the contact's information and the reason forthe information transfer.

Within each bucket 130, there may be contact folders for each contact,in which communications from all sources coming from that contact may bestored. FIG. 4D, for example, shows a display of contact folders fromwhich to choose and view communications from a certain contact. A system100 user may also make notes about the inbound or outboundcommunications and/or the relationship with that contact and store themin the contact folder for that contact. For example, FIG. 4F illustratesa contact folder for communications from a particular contact in whichthere are notes as well as a display of inbound and outgoing calls.Multiple phone numbers or other communications reception locations for acontact may be organized within a contact folder. The communicationstype and location (email address or phone number, for example) may belisted, for example in order of preference by the system 100 user. Notesmay also be made in any bucket 130 or other folder within system 100.Accordingly, all communications may be tracked and shown on a timelineas a summary of the system 100 user's communication relationship withthat contact. If system 100 user wishes, he can set certain types ofcommunications as priority to be shown first, whether it becommunications from a certain person or entity and/or a certain type ofcommunications from a person or entity. The system 100 may alsoprioritize inbound communications so that the system 100 useracknowledges and answers the most important communications first. Thisfunction may be accomplished by the system 100 user pre-determining whatcontact and/or type of relationship should receive priority. The system100 may then prioritize the new communications accordingly. If thesystem 100 user's relationship status with a contact changes or ends,(if their business dealings end, for example) the user may have theability to make a note of what happened and why the status with thatcontact has changed.

Communications are safely stored within system 100 and access ispassword protected. The system 100 user may allow others to have accessto the system information on their own device (smartphone, tablet, etc.)by giving the other people access. The degree of access for the otherpeople may be determined by the user, whether the access level be high,like that of an administrator (allowing edits to communications and/orinformation) or low, like that of a viewer (can only see thecommunications and/or information in the system 100). The degree ofaccess of another person to a system 100 user's information may bedetermined by the user. Once communications and information is safelystored in the data cloud, the system 100 user may archive and easilyretrieve the information and/or search for key words within a bucket 130or contact folder to easily locate the desired communications. As anillustration, recorded phone calls may be transcribed, and therefore,may be searchable via the system's 100 search function. Through thesearch function, all forms of communications stored within system 100are searchable within system 100. Also, displays before entering abucket 130 or contact folder may show how many unviewed messages orother types of communications exist in that bucket or contact folder(see FIG. 3), and relationship management engine 120 may be responsiblefor detecting such unviewed communications.

In addition to the foregoing, relationship management engine 120 mayhave other functions related to the reception, storage, organization,and prioritization of communications received from any source. Forexample, relationship management engine 120 may automatically recordphone calls as they are taking place based on the system 100 user'ssettings for that particular contact, or distribute inbound phone callsto multiple mobile phones that may also have system 100 running at thattime. Using geo-fencing, system 100 may be configured not to send a callto any system 100 user who may be too far away from a centralizedlocation, or other location determined by a system 100 user. Also, ifthe system 100 user is placing a call to a certain contact, the user canset the relationship management engine 120 to mask the outbound phonenumber. This function may also mask any other source-identifyinginformation in any type of outbound communications. This may beaccomplished by configuring system 100 to set the masking value for anoutbound phone number, email address, or any other source-identifyingcharacteristic of any type of communications. System 100 will then usethat configuration value to use for contact identification for incomingcommunications and/or for sending outbound communications.

With continued reference to FIG. 2, in various exemplary embodiments,work flow engine 140 is any engine, system, or method within system 100configured to analyze, take action upon, and/or display communicationsand information received by the relationship management system 100. Itshould be appreciated that the functions performed by relationshipmanagement engine 120 and work flow engine 140 may be performed inconjunction by a single component or system. Additionally, functionalityof relationship management engine 120 and/or workflow engine 140 may besupplemented by and/or implemented as inputs or configurations being setand/or performed manually by a system 100 user. Once communications areorganized and stored into its appropriate bucket(s) 130, workflow engine140 may analyze what action should be taken regarding each piece ofcommunications. Work flow engine 140 may look at system parameters, acontact's status, and/or time elapsed to perform certain actions toprompt the user to do something or automatically take appropriate actionas configured. For example, the application may send an email reminderor text message to a user about an appointment. A system 100 user maymake settings in the workflow engine 140 to govern operation thereof.For example, by utilizing system 100's administrative function, a system100 user may create settings and set-up pre-determined courses of actionin the case(s) of communications having certain characteristics (i.e.,contact source, communications type, age of communications, etc.).

For example, for emails received from certain contacts that containcertain content, the system 100 user may set the workflow engine 140 toautomatically reply with form emails. Workflow engine 140 may also beset to send communications automatically to certain contacts or allcontacts within a bucket 130. For example, if the system 100 user ismanaging a multifamily housing complex, on the first of each month, theworkflow engine 140 may be set to automatically email or text, forexample, all contacts in a “tenants” bucket on the last day of eachmonth. As another example, every contact in a “Lead” or “ProspectiveClient” bucket may automatically be sent communications notifying themof upcoming or present sales for the system 100 user's business.

Workflow engine 140 may also display reminders to the system 100 user ifa certain type of communications or communications from a certaincontact or contact type is not viewed or answered in a timely fashion.Workflow engine 140 may also move communications to other buckets basedon the communications and/or the contact's status or whether the system100 user has viewed or answered the communications. Communications mayremain within the same contact folder, and a contact folder may movebetween buckets 130.

A system 100 user may be able to set the appropriate amount of responsetime based on the contact and/or communications types. Similarly, if thesystem 100 user has not responded in the set amount of time, theworkflow engine 140 may be set by the system 100 user to transfer orshare the communications to a second system 100 user's communicationdevice (smartphone, tablet, etc.), so that second user may be able torespond to the contact's communications. The second user may then benotified via email or text message, for example, to take action. Also,one system 100 user may transfer an ongoing phone call, route anincoming call to a second system 100 user, or set the system 100 so thatincoming communications will be automatically routed to a second system100 user through the system 100. When a phone call is transferred, therecording of the call may continue on the second user's device(smartphone, tablet, etc.). Since all information is stored on thesystem 100 data cloud, any user within system 100 may access anyrecording on their electronic device (smartphone, tablet, etc.).

Workflow engine 140 may automatically schedule tasks set by the system100 user, such as tasks that must be performed periodically. Similarly,workflow engine 140 may automatically place tasks on the system 100user's calendar by identifying event names and associated times inreceived communications. System 100 will display possible calendarevents to the user, the user may accept the event, and then the event isadded to the calendar. If a system 100 user updates his calendar, sendsan email from a different device than the smartphone or tablet with thesystem 100, or if there are relevant informational updates detected onthe Internet or from other system 100 users, the system 100 willperiodically sync all accessible data onto the system 100 in order tokeep the information displayed by the system 100 in accordance withupdates from all accessible sources.

In system 100, interaction with a user may be via user interface 160.User interface 160 may comprise any suitable displays, windows,applications, apps, pop-ups, audio/visual content, and/or the like toallow a user to utilize functionality of system 100. In an exemplaryembodiment, user interface 160 comprises a mobile application. Inanother exemplary embodiment, user interface 160 comprises desktopsoftware. FIGS. 4A-4R illustrate exemplary screenshots of an exemplaryuser interface 160, illustrating how a user may access functionality ofsystem 100. FIGS. 5A-5P illustrate exemplary screenshots of anotherexemplary user interface 160, illustrating how a user may accessfunctionality of system 100.

User interface 160 may display any suitable information for a user. Forexample, the displays may include lists of buckets with contactrelationship statuses, contact names, communications types, notes withincommunications made by the system 100 user, etc. The user interface 160may also provide email templates created by the system 100 user, as wellas graphics that may be loaded onto emails or other forms ofcommunications. These templates and graphics may be stored in the system100, along with all other communications and information. Through thesedisplays on the user interface 160, the user may navigate thecommunications and information stored within the system 100 or createcommunications, for example by searching key words, navigating throughbuckets and contact lists, looking at calendar schedules or businessreports, or any number of appropriate actions. A system 100 user maysave, delete, archive, prioritize, move, copy, transfer to anothersystem 100 user, or perform any other suitable action to (or with)communications information associated with system 100.

Turning now to FIGS. 3A through 3F, in various exemplary embodiments asystem 100 may be configured with components, methods, and data flows asillustrated.

While examples may have been used above or shown in the figuresregarding the relationship management system's applicability to certainindustries, those examples herein should not be read to limit thepresent disclosure to such industries. Principles of the presentdisclosure may suitably be applied in connection with relationshipmanagement in various industries and/or contexts.

While the exemplary embodiments described herein are described insufficient detail to enable those skilled in the art to practiceprinciples of the present disclosure, it should be understood that otherembodiments may be realized and that logical and/or functional changesmay be made without departing from the spirit and scope of the presentdisclosure. Thus, the detailed description herein is presented forpurposes of illustration and not of limitation.

While the description references specific technologies, systemarchitectures and data management techniques, practitioners willappreciate that this description is of various embodiments, and thatother devices and/or methods may be implemented without departing fromthe scope of principles of the present disclosure. Similarly, while thedescription references a user interfacing with the system via a computeruser interface, practitioners will appreciate that applicable interfacesmay include mobile devices, kiosks and handheld devices such as mobilephones, smartphones, tablet computing devices, etc.

While the steps outlined herein represent exemplary embodiments ofprinciples of the present disclosure, practitioners will appreciate thatthere are any number of computing algorithms and user interfaces thatmay be applied to create similar results. The steps are presented forthe sake of explanation only and are not intended to limit the scope ofthe present disclosure in any way. Benefits, other advantages, andsolutions to problems have been described herein with regard to specificembodiments. However, the benefits, advantages, solutions to problems,and any element(s) that may cause any benefit, advantage, or solution tooccur or become more pronounced are not to be construed as critical,required, or essential features or elements of any or all of the claims.

It should be understood that the detailed description and specificexamples, indicating exemplary embodiments, are given for purposes ofillustration only and not as limitations. Many changes and modificationsmay be made without departing from the spirit thereof, and principles ofthe present disclosure include all such modifications. Correspondingstructures, materials, acts, and equivalents of all elements areintended to include any structure, material, or acts for performing thefunctions in combination with other elements. Reference to an element inthe singular is not intended to mean “one and only one” unlessexplicitly so stated, but rather “one or more.” Moreover, when a phrasesimilar to “at least one of A, B, or C” or “at least one of A, B, and C”is used in the claims or the specification, the phrase is intended tomean any of the following: (1) at least one of A; (2) at least one of B;(3) at least one of C; (4) at least one of A and at least one of B; (5)at least one of B and at least one of C; (6) at least one of A and atleast one of C; or (7) at least one of A, at least one of B, and atleast one of C.

What is claimed is:
 1. A relationship management system comprising: aprocessor in communication with a server; a tangible, non-transitorymemory configured to communicate with the processor, the tangible,non-transitory memory having instructions stored thereon that, inresponse to execution by the processor, cause the processor to performoperations comprising: receiving, at the server, a communicationcomprising a communication type, wherein the communication type includesan email, a text message, social media website post, manual entry and avoice call from a computing device; filtering, by a relationshipmanagement engine running on the server, the communication into a bucketfrom a plurality of buckets based on the communication type, businessrules, content characteristics and user settings and in response to thecommunication originating from a source contact associated with thebucket, wherein the content characteristics include phone number, emailaddress, social media account, and relationship between the sourcecontact and a user of a first user system; recording, by therelationship management engine, the communication into a profile of thesource contact that sent the communication, wherein all communicationsfrom the source contact are displayed together under a source contactsection; displaying, by the relationship management engine, thecommunication in a timeline with other communications from the sourcecontact; receiving, by the server and from the first user system, apriority preference based on the type of communication and the sourcecontact; displaying, by the server, the communications based on thepriority preference; receiving, by the server, an unknown communicationfrom an unknown contact; identifying, by the server, the unknowncommunication as a different communication type from the source contact;recording, by the relationship management engine, the unknowncommunication into the profile of the source contact; receiving, by therelationship management engine and from the first user system notesassociated with the communication, wherein the notes include a reasonfor transferring the source contact to a second user system;incorporating, by the relationship management engine, the notes into thecommunication; transferring, by the server, the source contact to thesecond user system; filtering, by the server, inbound phone calls todistribute a subset of the inbound phone calls to the first user systemand the second user system in response to the first user system and thesecond user system being within a geo-fence area; analyzing, by aworkflow engine running on the server, the communication to identify anaction to take in response to the communication, wherein the actioncomprises creating a calendar event; identifying in the communication,by the workflow engine, an event name and an event time of the calendarevent; creating, by the relationship management engine, a preset maskingvalue by determining a source-identifying value for an outboundcommunication; associating, by the relationship management engine, thepreset masking value with a profile of the source contact; masking, bythe relationship management engine, an outbound number andsource-identifying information of the outbound communication with thepreset masking value; sending, by the relationship management engine,the outbound communication with the preset masking value to the sourcecontact responsive to the communication, identifying, by therelationship management engine, a contact in an incoming communicationbased on the masking value; presenting, by a mobile softwareapplication, the calendar event for verification by the first usersystem; and storing the outbound communication in a database inassociation with the preset masking value.
 2. The relationshipmanagement system of claim 1, wherein the system is configured for usein connection with management of a multi-family housing industry.
 3. Therelationship management system of claim 1, wherein the system furthercomprises: the relationship management engine configured to filter aplurality of communications into the plurality of buckets using thepreset masking value for contact identification; and the workflow engineconfigured to analyze each of multiple forms of communication and selectfrom among a plurality of actions; wherein a user interface comprisesthe mobile software application, the mobile software applicationconfigured to communicate with the database and configured to allow thefirst user system to interact with the plurality of communications inthe plurality of buckets.
 4. The relationship management system of claim3, wherein when analyzing each of the multiple forms of thecommunication, the workflow engine utilizes system parameters, a statusof the source contact profile, and a time elapsed to select from amongthe plurality of actions.
 5. The relationship management system of claim4, wherein the plurality of actions comprise: automatically replying toan email; moving an item of communication from a first bucket into asecond bucket; and transferring a telephone call from a first mobiledevice to a second mobile device.
 6. A computerized method forrelationship management, the method comprising: receiving, at a server,a communication comprising a communication type, wherein thecommunication type includes an email, a text message, social mediawebsite post, manual entry and a voice call from a computing device;filtering, by a relationship management engine running on the server,the communication into a bucket from a plurality of buckets based on thecommunication type, business rules, content characteristics and usersettings and in response to the communication originating from a sourcecontact associated with the bucket, wherein the content characteristicsinclude phone number, email address, social media account, andrelationship between the source contact and a user of a first usersystem; recording, by the relationship management engine, thecommunication into a profile of the source contact that sent thecommunication, wherein all communications from the source contact aredisplayed together under the source contact; displaying, by therelationship management engine, the communication in a timeline withother communications from a source contact section; receiving, by theserver and from the first user system, a priority preference based onthe type of communication and the source contact; displaying, by theserver, the communications based on the priority preference; receiving,by the server, an unknown communication from an unknown contact;identifying, by the server, the unknown communication as a differentcommunication type from the source contact; recording, by therelationship management engine, the unknown communication into theprofile of the source contact; receiving, by the relationship managementengine and from the first user system notes associated with thecommunication, wherein the notes include a reason for transferring thesource contact to a second user system; incorporating, by therelationship management engine, the notes into the communication;transferring, by the server, the source contact to the second usersystem; filtering, by the server, inbound phone calls to distribute asubset of the inbound phone calls to the first user system and thesecond user system in response to the first user system and the seconduser system being within a geo-fence area; analyzing, by a workflowengine running on the server, the communication to identify an action totake in response to the communication, wherein the action comprisescreating a calendar event; identifying in the communication, by theworkflow engine, an event name and an event time of the calendar event;creating, by the relationship management engine, a preset masking valueby determining a source-identifying value for an outbound communication;associating, by the relationship management engine, the preset maskingvalue with a profile of the source contact; masking, by the relationshipmanagement engine, an outbound number and source-identifying informationof the outbound communication with the preset masking value; sending, bythe relationship management engine, the outbound communication with thepreset masking value to the source contact responsive to thecommunication, identifying, by the relationship management engine, acontact in an incoming communication based on the masking value;presenting, by a mobile software application, the calendar event forverification by the first user system; and storing the outboundcommunication in a database in association with the preset maskingvalue.
 7. The method of claim 6, further comprising displaying a userinterface on a mobile device running the mobile software application incommunication with the server, wherein the relationship managementengine is configured to manage multiple forms of communicationinformation associated with the source contact to send notifications,schedule tasks, and allow the user to see reports.
 8. The method ofclaim 7, wherein the relationship management system further comprises:filtering, by the relationship management engine the multiple forms ofcommunication information into the plurality of buckets; and analyzing,by the workflow engine each of the multiple forms of communication;selecting, by the workflow engine, the action from a plurality ofactions; interacting, by the mobile software application, with thedatabase to retrieve the multiple forms of communication information inthe plurality of buckets.
 9. The method of claim 7, wherein whenanalyzing each of the multiple forms of the communication, the workflowengine utilizes system parameters, a status of a contact, and a timeelapsed to select the action from the plurality of actions.
 10. Themethod of claim 9, wherein the action comprises at least one of:automatically replying to an email; moving a communication from a firstbucket into a second bucket; or transferring a telephone call from afirst mobile device to a second mobile device.
 11. The method of claim7, wherein the multiple forms of communication information comprisetelephone calls, emails, text messages, and social media communications.12. The method of claim 7, wherein the relationship management engine isconfigured for use in connection with management of a multi-familyhousing industry.
 13. An article of manufacture including anon-transitory, tangible computer readable storage medium havinginstructions stored thereon that, in response to execution by a server,cause the server to perform operations comprising: receiving, at theserver, a communication comprising a communication type, wherein thecommunication type includes an email, a text message, social mediawebsite post, manual entry and a voice call from a computing device;filtering, by a relationship management engine running on the server,the communication into a bucket from a plurality of buckets based on thecommunication type, business rules, content characteristics and usersettings and in response to the communication originating from a sourcecontact associated with the bucket, wherein the content characteristicsinclude phone number, email address, social media account, andrelationship between the source contact and a user of a first usersystem; recording, by the relationship management engine, thecommunication into a profile of the source contact that sent thecommunication, wherein all communications from the source contact aredisplayed together under the source contact; displaying, by therelationship management engine, the communication in a timeline withother communications from a source contact section; receiving, by theserver and from the first user system, a priority preference based onthe type of communication and the source contact; displaying, by theserver, the communications based on the priority preference; receiving,by the server, an unknown communication from an unknown contact;identifying, by the server, the unknown communication as a differentcommunication type from the source contact; recording, by therelationship management engine, the unknown communication into theprofile of the source contact; receiving, by the relationship managementengine and from the first user system, notes associated with thecommunication, wherein the notes include a reason for transferring thesource contact to a second user system; incorporating, by therelationship management engine, the notes into the communication;transferring, by the server, the source contact to the second usersystem; filtering, by the server, inbound phone calls to distribute asubset of the inbound phone calls to the first user system and thesecond user system in response to the first user system and the seconduser system being within a geo-fence area; analyzing, by a workflowengine running on the server, the communication to identify an action totake in response to the communication, wherein the action comprisescreating a calendar event; identifying in the communication, by theworkflow engine, an event name and an event time of the calendar event;creating, by the relationship management engine, a preset masking valueby determining a source-identifying value for an outbound communication;associating, by the relationship management engine, the preset maskingvalue with a profile of the source contact; masking, by the relationshipmanagement engine, an outbound number and source-identifying informationof the outbound communication with the preset masking value; sending, bythe relationship management engine, the outbound communication with thepreset masking value to the source contact responsive to thecommunication, identifying, by the relationship management engine, acontact in an incoming communication based on the masking value;presenting, by a mobile software application, the calendar event forverification by the first user system; and storing the outboundcommunication in a database in association with the preset maskingvalue.